Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1753

reference
481-tree-1
name
1753
tree-preservation-order

undefined

481-tpo-1
uprn
address-text
point
POINT (-1.022687 50.884761)
geometry
MULTIPOLYGON (((-1.022630 50.884755,-1.022633 50.884766,-1.022641 50.884776,-1.022653 50.884784,-1.022669 50.884790,-1.022687 50.884791,-1.022704 50.884790,-1.022720 50.884785,-1.022733 50.884777,-1.022741 50.884767,-1.022744 50.884756,-1.022742 50.884745,-1.022734 50.884735,-1.022721 50.884727,-1.022706 50.884721,-1.022688 50.884719,-1.022670 50.884721,-1.022654 50.884726,-1.022642 50.884734,-1.022633 50.884744,-1.022630 50.884755)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL